<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Compiling GTK+ Applications</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="GTK+ 2 Reference Manual">
<link rel="up" href="gtk.html" title="Part I. GTK+ Overview">
<link rel="prev" href="gtk-building.html" title="Compiling the GTK+ libraries">
<link rel="next" href="gtk-running.html" title="Running GTK+ Applications">
<meta name="generator" content="GTK-Doc V1.18 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
<td><a accesskey="p" href="gtk-building.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
<td><a accesskey="u" href="gtk.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
<th width="100%" align="center">GTK+ 2 Reference Manual</th>
<td><a accesskey="n" href="gtk-running.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="gtk-compiling"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">Compiling GTK+ Applications</span></h2>
<p>Compiling GTK+ Applications — 
How to compile your GTK+ application
</p>
</td>
<td valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1">
<a name="id462417"></a><h2>Compiling GTK+ Applications on UNIX</h2>
<p>
To compile a GTK+ application, you need to tell the compiler where to 
find the GTK+ header files and libraries. This is done with the
<code class="literal">pkg-config</code> utility.
</p>
<p>
The following interactive shell session demonstrates how
<code class="literal">pkg-config</code> is used (the actual output on 
your system may be different):
</p>
<pre class="programlisting">
$ pkg-config --cflags gtk+-2.0
 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/atk-1.0  
$ pkg-config --libs gtk+-2.0
 -L/usr/lib -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -lXi -lgdk_pixbuf-2.0 -lm -lpangox -lpangoxft -lXft -lXrender -lXext -lX11 -lfreetype -lpango -latk -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0  
</pre>
<p>
</p>
<p>
The simplest way to compile a program is to use the "backticks"
feature of the shell. If you enclose a command in backticks
(<span class="emphasis"><em>not single quotes</em></span>), then its output will be
substituted into the command line before execution. So to compile 
a GTK+ Hello, World, you would type the following:
</p>
<pre class="programlisting">
$ cc `pkg-config --cflags --libs gtk+-2.0` hello.c -o hello
</pre>
<p>
</p>
<p>
If you want to make sure that your program doesn't use any deprecated 
functions, you can define the preprocessor symbol GTK_DISABLE_DEPRECATED
by using the command line option <code class="literal">-DGTK_DISABLE_DEPRECATED=1</code>.
There are similar symbols GDK_DISABLE_DEPRECATED, 
GDK_PIXBUF_DISABLE_DEPRECATED and G_DISABLE_DEPRECATED for GDK, GdkPixbuf and
GLib. 
</p>
<p>
If you want to make sure that your program doesn't use any functions which 
may be problematic in a multihead setting, you can define the preprocessor
symbol GDK_MULTIHEAD_SAFE by using the command line option 
<code class="literal">-DGTK_MULTIHEAD_SAFE=1</code>.
</p>
<p>
The recommended way of using GTK+ has always been to only include the
toplevel headers <code class="filename">gtk.h</code>, <code class="filename">gdk.h</code>, 
<code class="filename">gdk-pixbuf.h</code>.
If you want to make sure that your program follows this recommended
practise, you can define the preprocessor symbols GTK_DISABLE_SINGLE_INCLUDES
and GDK_PIXBUF_DISABLE_SINGLE_INCLUDES to make GTK+ generate an error
when individual headers are directly included.
There are some exceptions: <code class="filename">gdkkeysyms.h</code> is not included in
<code class="filename">gdk.h</code> because the file is quite large; see
<a href="../gdk/gdk-Keyboard-Handling.html">Key Values documentation</a>.
<code class="filename">gdkx.h</code> must be included independently because It's
platform-specific; see
<a href="../gdk/gdk-X-Window-System-Interaction.html">X Window System Interaction</a>
documentation.
The same for <code class="filename">gtkunixprint.h</code> if you use the non-portable
<a class="link" href="GtkPrintUnixDialog.html" title="GtkPrintUnixDialog">GtkPrintUnixDialog</a> API.
</p>
<p>
The next major version, GTK+ 3,  will remove many implementation details and
struct members from its public headers. To ensure that your application will
not have problems with this, you can define the preprocessor symbol
GSEAL_ENABLE. This will make the compiler catch all uses of direct access to
struct fields so that you can go through them one by one and replace them with
a call to an accessor function instead.
</p>
</div>
</div>
<div class="footer">
<hr>
          Generated by GTK-Doc V1.18</div>
</body>
</html>